Description

Centralize frontend logging behind a dedicated logger utility, replace direct console.* usage across the frontend, and enforce the pattern through ESLint.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🧪 Test addition or update

Related Issues

Closes #628

Changes Made

• Added frontend/src/lib/logger.ts as a centralized logging utility
• Replaced direct console.error, console.warn, and console.info calls with logger helpers
• Updated frontend modules to use the shared logger
• Added ESLint enforcement to forbid raw console.* usage outside the logger module
• Cleaned up additional console usages found in src/utils/amount.ts

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Steps

1. Run npm run lint
2. Verify lint passes with current changes
3. Add a temporary console.log(...) statement in a frontend source file
4. Run npm run lint and verify the no-console rule is triggered
5. Remove the temporary statement and verify lint passes again

Breaking Changes

Breaking Changes:

• None

Migration Guide:

• No migration required

Screenshots/Demo

N/A

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have checked for breaking changes and documented them if applicable

Additional Notes

• Existing test failures in src/components/stream-creation/__tests__/template-storage.test.ts appear to be unrelated to this change and are caused by a pre-existing localStorage.clear is not a function error.
• Logging behavior is now centralized, making future changes to frontend logging easier to manage.